Print

This update requires you to make changes to the following files:

• /Web.config
• /App_Config/Include/Sitecore.Analytics.config

The clean config files for Sitecore CMS 6.5.0 and DMS 2.0.1 rev. 120706 can be downloaded using the following links:

• Sitecore CMS 6.5.0 rev. 120706 Web.config file 
• Sitecore DMS 2.0.1 rev. 120706 Analytics.config file 

Changes to the Web.config file

The following changes have been made to the Web.config file of Sitecore CMS 6.5.0 rev. 120706 (Service Pack 1) as compared to the Web.config file of Sitecore CMS 6.5.0 rev. 120427 (Update-4):

1. In the <sitecore><databases><database id="web"> section, remove the NotificationProvider node. The section now looks like this in a default Sitecore installation:
   <database id="web" singleInstance="true" type="Sitecore.Data.Database, Sitecore.Kernel">
     <param desc="name">$(id)</param>
     <icon>Network/16x16/earth.png</icon>
     <securityEnabled>true</securityEnabled>
     <dataProviders hint="list:AddDataProvider">
       <dataProvider ref="dataProviders/main" param1="$(id)">
         <disableGroup>publishing</disableGroup>
         <prefetch hint="raw:AddPrefetch">
           <sc.include file="/App_Config/Prefetch/Common.config" />
           <sc.include file="/App_Config/Prefetch/Web.config" />
         </prefetch>
       </dataProvider>
     </dataProviders>
     <proxiesEnabled>false</proxiesEnabled>
     <proxyDataProvider ref="proxyDataProviders/main" param1="$(id)" />
     <archives hint="raw:AddArchive">
       <archive name="archive" />
       <archive name="recyclebin" />
     </archives>
     <cacheSizes hint="setting">
       <data>20MB</data>
       <items>10MB</items>
       <paths>500KB</paths>
       <standardValues>500KB</standardValues>
     </cacheSizes>
   </database>
   You should keep the NotificationProvider nodes for the master and core databases.
   
2. In the <settings> section, add the following setting:
   <!--  PAGE STATE STORE
         Specifies the type responsible for storing SheerUI page state. 
         Must implement the IPageStateStore interface. 
         Possible values are "DatabasePageStateStore" or "FilePageStateStore".
         Default value: Sitecore.Web.UI.Sheer.FilePageStateStore, Sitecore.Kernel
   -->
   <setting name="PageStateStore" value="Sitecore.Web.UI.FilePageStateStore, Sitecore.Kernel" />
   
3. In the <settings> section, update the comment for the setting "ViewStateStore":
   <!--  VIEWSTATE STORE
         Specifies the type responsible for storing SheerUI viewstate. 
         Must implement the IViewStateStore interface. 
         Possible values are "DatabaseViewStateStore" or "FileViewStateStore".
         Default value: Sitecore.Web.UI.Sheer.FileViewStateStore,Sitecore.Kernel
   -->
   <setting name="ViewStateStore" value="Sitecore.Web.UI.Sheer.FileViewStateStore,Sitecore.Kernel" />
   

Changes to the Sitecore.Analytics.config file

The following changes have been made to the Sitecore.Analytics.config file of DMS 2.0.1 rev. 120706 as compared to the Sitecore.Analytics.config file of DMS 2.0.1 rev. 120427.

1. The default value for the "Analytics.Automation.BatchSize" setting has been changed from 1000 to 10. Change the value of this setting from 1000 to 10 unless you have set it to a different value:
   <!--  ANALYTICS AUTOMATION BATCH SIZE
         Defines the number of records to process in a batch.
         Default: 10
   -->
   <setting name="Analytics.Automation.BatchSize" value="10" />
   
2. In the <settings> section, add the following setting:
   <!--  ANALYTICS AUTOMATION LOCK EXPIRATION 
         When Sitecore processes automation states, the system marks the rows in the database
         that it is about to process. If, for
         some reason, the states are not successfully processed, 
         the rows will be processed again at a later time.
         This can happen, for example, if the server restarts while rows are being processed.
         This setting specifies the minimum wait time (in seconds) before the rows
         can be selected for re-processing.
         Default: 3 (3 seconds)
   -->
   <setting name="Analytics.Automation.LockExpiration" value="3" />
   
3. In the <automation> pipeline, remove the node of type LastAccessedDateTime. The <automation> pipeline now looks like this in a default Sitecore installation:
   <automation>
     <processor type="Sitecore.Analytics.Pipelines.Automation.GetAutomationStateItem, Sitecore.Automation.MarketingAutomation" />
     <processor type="Sitecore.Analytics.Pipelines.Automation.ProcessCommands, Sitecore.Automation.MarketingAutomation" />
     <processor type="Sitecore.Analytics.Pipelines.Automation.SetNextWakeUpTime, Sitecore.Automation.MarketingAutomation" />
   </automation>
   
4. In the <acceptChanges> pipeline, add a node for a new processor of type UpdateAutomationStates, between the DropCancelledPage and AcceptSharedChanges processors. The <acceptChanges> pipeline now looks like this in a default Sitecore installation:
   <acceptChanges>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.DoNotWrite, Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.Robots, Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.GeneratingCampaignEvents, Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.DropCancelledPage, Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.UpdateAutomationStates, Sitecore.Automation.MarketingAutomation"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.AcceptSharedChanges, Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.AcceptVisitorChanges, Sitecore.Analytics"/>
   </acceptChanges>